Skip to content

Fix stale Bitcoin command names in user-facing messages#336

Open
been3p-prog wants to merge 1 commit into
BitgesellOfficial:masterfrom
been3p-prog:bgl-user-facing-command-names
Open

Fix stale Bitcoin command names in user-facing messages#336
been3p-prog wants to merge 1 commit into
BitgesellOfficial:masterfrom
been3p-prog:bgl-user-facing-command-names

Conversation

@been3p-prog
Copy link
Copy Markdown

Summary

  • Replace stale Bitcoin executable names in user-facing messages with Bitgesell command names.
  • Update daemon, Qt, RPC help, and chainstate restart guidance strings.

Changed strings

  • bitcoind -h -> BGLd -h
  • bitcoin-qt -h -> BGL-qt -h
  • bitcoin-cli -rpcclienttimeout=0 -> BGL-cli -rpcclienttimeout=0
  • restart bitcoind -> restart BGLd

Validation

  • git diff --check
  • Searched changed files to confirm the replaced stale strings no longer remain.

Bounty context

@MyTH-zyxeon
Copy link
Copy Markdown

Review-assist note for the Bitgesell PR bounty queue (#32) and the broader #81 improvement program.

I checked the public diff for this PR. Scope is narrow and user-facing only:

  • replaces stale Bitcoin executable names in runtime/help strings with Bitgesell command names (BGLd, BGL-qt, BGL-cli)
  • touches daemon/Qt/RPC/chainstate guidance strings only
  • does not change consensus, wallet signing, RPC behavior, chainstate recovery logic, or build configuration

Suggested maintainer checks before approval:

  • confirm BGLd, BGL-qt, and BGL-cli are the canonical binary names the project wants in user-facing help/error text
  • run a quick grep for nearby remaining stale bitcoind, bitcoin-qt, and bitcoin-cli strings so this PR does not land a partial terminology cleanup if adjacent messages should move together
  • treat payout under BGL PR bounty hunt #32 as a small docs/user-message cleanup unless maintainers want to bundle it with a larger naming-consistency pass

From the public patch shape, this looks like a low-risk, reviewable PR in the bounty queue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants